late binding

Late binding of a service's access point is one use of an UDDI registry that is common today.

服务访问点的延迟绑定（late binding）是目前UDDI注册中心的常见用途之一。

Fabric eliminates the need for hard-coded static binding of services and provides late binding of services to enable more generalized process models.

Fabric消除了对硬编码的静态服务绑定的需要，并提供了后期服务绑定以支持更加泛化的流程模型。

This is enabled by the late binding of declared interfaces to implementations supporting those interfaces.

通过将声明的接口延迟绑定到支持这些接口的实现可以做到这一点。

Implementation technologies of SDAI session, access to remote repository, data dictionary and late binding are also described.

还阐述了用EJB实现SDAI会话，访问远程repository以及SDAI数据字典和迟联编的实现机制。

The late binding of the service endpoint address lowers the location coupling.

服务端点地址的后期绑定降低了位置耦合。

It also gives two practical application cases of early binding and late binding.

提供了早绑定和迟绑定具体应用的实例。

A partial version of core services written in Visual Basic also exists for runtime compilation and late binding.

为了支持运行时编译和迟绑定，由Visual Basic编写的核心服务的部分版本也是存在的。

It's slightly complicated by the late binding to release vehicles for task branches.

通过后期绑定到任务分支的版本媒介物上稍微有一些复杂。

This is often referred to as runtime binding or late binding.

这通常被称为运行时绑定或延迟绑定。

Support for dynamic lookup is already available in Visual Basic for. NET, where it is often known as "late binding".

实际上，VB.NET中已经对动态查找提供了支持，不过它的动态查找通常被叫做延迟绑定（late binding）。

This is seen in mismatched language features such as the ability to consume objects via late binding, a.k.a.duck typing, but no ability to define them.

例如，它能够通过迟绑定（即所谓的duck typing）来使用对象，但却没有能力确定他们&这样的语言特性被普遍认为是和脚本编程是不相配的。

Be wary of late binding to a name that includes some user data.

在后期绑定到包含某些用户数据的名称时要多加小心。

The answer to this challenge is the use of registry-based "late binding".

对这个挑战的回答是基于注册中心的“延迟绑定”。

The only supported combination for late binding is if a process component calls another process component.

唯一受支持的后期绑定组合是一个流程组件调用另一个流程组件。

In reality many SOA practitioners have been introducing service registry as a mechanism for late binding and dynamic routing.

实际上，很多SOA专业人员都已经将服务注册中心作为用于进行后期绑定和动态路由的机制加以引入了。

Support for early binding and late binding

早期绑定和后期绑定支持

Late binding makes this structure possible.

正是后期绑定让这一切成为可能。

There are many reasons you should avoid late binding, including slower application performance.

由于包括应用程序性能降低在内的多种原因，应该避免后期绑定。

What you need is late binding.

而您所需要的是延后绑定。

In general, methods that take a process template name as a parameter use late binding.

一般来讲，接受流程模板名称作为参数的方法使用后期绑定。

Demonstrates how to implement late binding.

演示如何实现后期绑定。

In other words, Web service invocation ought to be of late binding.

换句话说，Web服务调用应该在后期绑定。

This section describes where you have the option to choose from early binding and late binding.

本部分描述您可以从早期绑定和后期绑定中做出选择的场合。

You could certainly handle late binding through Java's reflection API.

您当然可以通过Java的反射API处理后期绑定。

Of particular interest is the way it handles late binding, more commonly known today as "duck typing".

其最能引起大家兴趣的地方在于它处理“晚绑定（late binding）”的方式，现在我们通常称其为“duck typing”。

Web services enable just-in-time integration by promoting loose coupling and late binding.

Web服务通过提升松散耦合和延时绑定来实现即时集成。

How to speed up in a late binding world.

如何在迟绑定的环境下提速。

Unlike most languages that either always or never use late binding, Boo allows developers to declare specific variables as late bound.

不像大多数语言&要么总使用晚绑定，要么从来不用，Boo允许开发者声明特定的变量来进行晚绑定。

A type library must be registered before the runtime can see it, except in the case of late binding.

除后期绑定的情况外，类型库必须在运行库可以查看它之前注册。

VB does with late binding, but again that opens the possibility for missing method exceptions.

VB则是通过延迟绑定来实现的这个功能，不过这也带来了“missing method exception”之类的问题。